Temporary messaging address system and method

ABSTRACT

A messaging system is disclosed. The system includes a communications network including a wireless access point, a messaging server coupled to the communications network, and a mobile device in communication with the communications network via an access point. The mobile device has a mobile ID associated with the device, and a program running on the mobile device from which a temporary address may be created corresponding to the mobile ID. The temporary address is useable for messaging over the communications network. The temporary address is registered with the messaging server.

BACKGROUND

The traditional messaging systems (email and instant messaging) aredesigned around the philosophy of a fixed messaging server and staticmessaging addresses through which messages may be sent to reach theintended user. Once a messaging address is known, it may be usedrepeatedly to send messages. The address may also be used independent oftime and location of either the sender or recipient.

In a more mobile environment, where users are using mobile wirelessdevices (such as a handheld or portable computer), traditional messagingsystems may not be optimal. While the idea of a static messaging addressis appealing, it is often not the most practical. Once a messagingaddress has been given out, there is no explicit mechanism to change orrevoke an address. To revoke an address, the user must either cancel themessaging account (or no longer access it), or filter out messages fromunwanted users. The former mechanism requires the user to notify peopleof a change in address (for those that should still be able to sendmessages), and the latter requires complex software and constantconfiguration on the client side. In addition, the second method placesan increased load on the mobile device and its communication links.

An additional problem for messaging in a mobile network environment isthe use of localized resources and ad hoc networks.

Accordingly, there is a need for a messaging system in a mobile networkwhich utilizes temporary messaging addresses associated with uniquemobile identifications.

There is also a need for a messaging server that is enabled to associatetemporary messaging addresses with mobile devices. Further, there is aneed for a method of communicating between a first mobile communicationsdevice and a second mobile communications device using temporarymessaging addresses and, further, depending on specified conditions.Further still, there is a need for a method of alerting patrons ofavailable services by utilizing temporary messaging addresses associatedwith individual mobile devices.

It would be desirable to provide a system and/or method that providesone or more of these or other advantageous features. Other features andadvantages will be made apparent from the present specification. Theteachings disclosed extend to those embodiments which fall within thescope of the appended claims, regardless of whether they accomplish oneor more of the aforementioned needs.

SUMMARY

An exemplary embodiment of the invention relates to a messaging system.The messaging system includes a communications network including awireless access point, a messaging server coupled to the communicationsnetwork, and a mobile device in communication with the communicationsnetwork via an access point. The mobile device has a mobile IDassociated with the device and a program running on the mobile devicefrom which a temporary address may be created corresponding to themobile ID. The temporary address is useable for messaging over thecommunications network the temporary address being registered with themessaging server.

Another exemplary embodiment of the invention relates to a method ofproviding messaging services to a user of a mobile communicationsdevice. The method includesproviding a mobile device having a mobile IDassociated therewith and running a messaging program on the device. Themethod also includes creating, via the program, a temporary messagingaddress, communicating the temporary messaging address to a messagingserver, and sending a message using the temporary messaging address.

Further, an exemplary embodiment of the invention relates to a messagingserver. The messaging server includes a protocol adapter for receivingmessages from mobile communications devices, each mobile communicationsdevice having a unique mobile ID associated therewith, a messaging queuefor ordering the delivery of incoming and outgoing messages, sent fromthe mobile communications devices, and an address translator enabled todetermine the mobile ID associated with the temporary delivery addressidentified in the incoming message.

Further still, an exemplary embodiment of the invention relates to amethod of alerting a patron of an available service. The method includescreating a temporary messaging address associated with a mobile devicehaving a unique mobile ID and sending a message to the temporary addressthrough a server. The message includes a notification of the serviceavailability. The method also includes translating the temporarymessaging address to the mobile ID, by the server, and sending themessage to the mobile device associated with the mobile ID.

Yet still another exemplary embodiment of the invention relates to amethod of communicating between a first mobile communications device anda second mobile communications device. The method includes creating afirst temporary messaging address associated with the first mobilecommunications device, creating a second temporary messaging addressassociated with the second mobile communications device, and providingconditions under which messages may be delivered between the twodevices. The method also includes sending a message from the firstmobile communications device to the second mobile communications deviceusing the second temporary messaging address, determining if theconditions for sending the message are satisfied, and delivering themessage to the second temporary address if the conditions are satisfied.

Alternative exemplary embodiments relate to other features andcombination of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will become more fully understood from the followingdetailed description, taken in conjunction with the accompanyingdrawings, wherein like reference numerals refer to like elements, inwhich:

FIG. 1 is a block diagram of a messaging server;

FIG. 2 is a block diagram of a messaging system; and

FIG. 3 is a block diagram of a communications system.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

If a mobile user wants to have messaging capabilities with users in alocalized geographical area it may be advantageous to use localizedservers and addresses. This would offer the following advantages:

-   -   Better performance, less performance problems from larger area        networks (e.g., delay, bandwidth).    -   Lack of global networking connections. Often a local area may        offer a localized network with no general internet connectivity.        Messaging could be accomplished via local servers with temporary        addresses. This may especially be applicable in ad hoc networks.    -   The ability to explicitly exploit location and time information        in messaging.    -   The ability to use, modify, or revoke messaging addresses.    -   The ability to switch from local to global messaging servers        (use local service when available, but switch to global when        leaving local area).

A mobile user may also have more than one mobile device (e.g., cellphone, PDA, pager, etc). Each one of these devices may be used forcommunication to the mobile user. In addition, the mobile user may havea preference as to which is used. It should be possible for a mobileuser to register multiple devices, but specify a preference to which isused. In addition, some mobile devices do not permit directcommunications between servers and devices (e.g., cell phones andpagers). Messages to these device may need to be passed through anexternal service (e.g., telephone system). This document discussesprimarily data devices and local wireless devices, but the system andideas disclosed may be applied to other, larger coverage area wirelesstechnologies.

The disclosure relates to a system by which messaging addresses can bedynamically assigned to allow more user control over messaging. A systemis available which can dynamically create new messaging addresses for amobile user on demand. The mobile user can give out different messagingaddresses to different people, and can revoke (cancel) an addressanytime thereby preventing messages from reaching the user.

This messaging system also is ideally suited for localized messaging, asmight be found in a shopping mall or other sites in which localizedmessaging may be useful.

A further component of a messaging system of the type disclosed is theuse of location and time specification in message submission. When amessage is sent, it may include both time and location conditions.Messages will only be delivered if the mobile user is in the specifiedlocation at the specified time.

The messaging system disclosed may include any one of or any combinationof the following characteristics:

-   -   1. The mail recipient has control over the duration of existence        of the messaging address.    -   2. Should support both e-mail (time insensitive), and instant        messaging (time sensitive) standards.    -   3. The system should preventspam (e-mail from unknown people) or        unauthorized messages.    -   4. The system should support existing email and messaging        standards.    -   5. Messages should be cancelable by the sender.    -   6. People can request to be notified of cancelled addresses.    -   7. Users can cancel mail addresses at anytime.    -   8. Messaging system can not be used for tracking.    -   9. A mobile user can use multiple messaging addresses.

Associated with each mobile device may be one or more mobile IDS. Amobile ID may be a universal resource locator (URL) which specifies thelocation of services for a mobile device or any other unique identifierassociated with an individual mobile device. URLs provide a standardformat for specifying a resource (message service) independent ofspecific service or protocol. Examples include but are not limited to:

-   -   mailto:customer1@mall.com    -   instantMessage://mobile.mall.com/customer1    -   email://customer1.mall.com    -   message:customer1@xxx.yyy.com

The mobile ID may be used for services other than messaging and providesa common format for such services. As an example, a mobile device may beassigned mobile ID:

-   -   MobileID://mobile.mall.com/customer1        The email or instant messaging address could be obtained from        the Mobile ID by replacing the protocol specification with the        appropriate services requested. For example:    -   Email://mobile.mall.com/customer1

The system may be configured to support two (or more) types ofaddressable entities, such as mobile devices and mobile users.

A mobile user may have multiple mobile devices (e.g., a laptop computer,a handheld computer, a pager, a mobile telephone, etc.). Messages may beredirected between the different mobile devices (e.g., e-mail messagesredirected to a pager).

Referring now to FIG. 1, in an exemplary embodiment a messaging server100 may be a localized server which provides messaging services. It maybe responsible for receiving messages, buffering messaging, and sendingmessages to the mobile devices among other tasks.

The architecture of message server 100 includes two processing queues.The first queue (processing queue 110) holds incoming messages 105 andmessages waiting for condition (location and time) satisfaction. Amessage is removed from the queue when all conditions are satisfied, forexample, time and/or location conditions.

An address translator 120 is responsible for translating an address ofmessage 105. The mobile ID of message 105 is converted into an addressused for delivery to a mobile device 125. Address translator 120 mayalso be used to redirect messages to different mobile devices (ifspecified by the mobile user).

A delivery queue holds messages until the mobile ID can be translatedinto a physical address. The delivery queue may include a push deliveryqueue 130 and a pull delivery queue 135. The push delivery queueattempts to deliver a message when mobile device 125 is accessible. Ifmobile device 125 is unavailable, the message is held in this queueuntil a physical address is available. Pull delivery queue 135 is usedfor queuing messages which must be pulled by the client. Messages arestored until requested by the client. The queue may support legacyprotocols, such as but not limited to IMAP, POP or others.

Mobile device events are notifications in the change of location (orother properties) of mobile device 125. These events are used to triggerthe condition of messages waiting in the processing queue. A mobiledevice state information unit 140 keeps track of the current location ofmobile device 125 and its current physical address. The current locationmay be supplied through a location determination service on or linked tothe network.

A mobile ID control unit 145 is responsible for keeping track of mobileIDs. Messages may also be sent to mobile device control unit 145. Thesemessage represent control messages used to allocate, modify, and changemobile IDs.

Acknowledgement messages (containing a message ID) are sent once themessage has left the delivery queue.

The basic functionality of the server may include but is not limited to:

-   -   Support existing messaging standards. The server can act as a        server for existing messaging protocols. For example IMAP, POP,        Instant Messaging (Jabber, AOL, MS, etc).    -   Receive location events. When the network detects that a mobile        device has moved location, a location event is sent to message        server 100. The condition on pending messages are evaluated to        see if they should be released. For example, notification of        when the mobile device moves and/or sending messages on        condition evaluation.    -   Buffering messages. For example, messaging waiting for events        and/or messaging waiting for delivery.    -   Receive message. For example, return message ID, and/or make or        contain time and location conditions.    -   Cancel message. For example, message specified by message ID.    -   Send message. For example, return messages associated with        mobile ID.    -   Direct messages. For example, the message server can forward        messages to another server.    -   Revoke message address. For example, turn off a message address.    -   Message delivery confirmation. For example, recipient        controlled.

The protocol adapters are used to support the different protocols andencoding with different existing messaging systems.

In an exemplary embodiment, the following communications may besupported by message server 100:

-   -   Register mobile_user, used to register a mobile user.    -   Register mobile_device, used to register amobile_device.    -   Set mobile_user preferences, such as a message describing any        processing to be applied to messages, for example, message        redirection and/or message filtering.    -   Send message, used to send a message.    -   Receive message, used to get a message.    -   Unregistermobile_user, used to cancelmobile_user and all        associated mobile_devices.    -   Unregistermobile_ID, used to cancel mobile_ID.    -   Query messageServer, used to get a description of message server        capabilities and configurable capabilities.

In an exemplary embodiment, the messaging client such as mobile device125 should support the following operations:

-   -   Send message wherein theMessage_ID may be returned.    -   Receive/display message.    -   Create new mobile_ID.    -   Delete mobile_ID.    -   Location specification.    -   Time specification.    -   Cancel message.    -   View all messages including those deleted and/or including those        waiting for events.

Further, in an exemplary embodiment a legacy messaging application 210(see FIG. 2) may be augmented with a client assist application 220.

The system should be compatible with existing messaging systems.Likewise, existing messaging clients should be compatible with thissystem, although full functionality may or may not be possible.

Referring now to FIG. 3, messaging server 100 is coupled to a localcommunications network 310 for sending messages to users connected tolocal communications network 310 or, alternatively, to an externalcommunications network 320. As described above, local communicationsnetwork 310 includes access points 330 that provide wireless access frommobile devices 340 to local communications network 310. In the exemplaryembodiments disclosed, mobile device 340 is enabled to create temporaryaddresses utilized by devices accessing local communications network 310via messaging server 100.

The mobile ID can be used to determine the email or instant messagingaddress of the mobile user. These addresses can be passed to existingemail and instant messaging systems so that they can send messages.

Any e-mail or instant messaging client can be used to send messaging inthis system.

The mobile user can also use standard instant messaging/email clients.The client application would need to be configured to bind themselves tothe proper servers, and supply correct user ID/passwords for messageretrieval. Not all existing messaging client support multiple addresses.

A legacy e-mail 210 or instant messaging system may be unable to specifylocation specific properties of a message, cancel messages, or benotified of address cancellation as the existing application andprotocol do not typically support these types of operations.Accordingly, messaging assist application 220 may provide an interfacefor e-mail application 210 and message server 100, wherein messageserver 100 is enabled to handle mobile users using temporary messagingaddresses.

In yet a further exemplary embodiment, a cell phone voice system may beaccessible through a plain old telephone system (POTS). Voice calls maybe sent through the telephone system and a mobile user would need toregister the telephone number. Voice messages may also be sent throughthe POTS and a mobile user needs to register the telephone number. Textmessages (e.g., SMS) may also be sent through a carrier message serviceand a mobile user needs to register a message address. Further, pagermessages may be sent through the POTS of message service and a mobileuser needs to register a telephone number or message service address.

When a message is sent, location conditions may be placed on themessage. Location may be specified in many ways, including but notlimited to, absolute coordinates (GPS, latitude, longitude), relativecoordinates (to message server, mobile device, or other objects), zones(location specific zones), transitions into or out of zones, and otherformats.

Location specifications may not be allowed which enable tracking. It maybe valid for a mobile user 1 to specify that a message should be sent tomobile user 2 when they are within 100 meters, but not valid for mobileuser 1 to request a message to be sent to himself when they are morethan 100 meters apart. This could only be done with cooperation ofmobile user 2. The location information may be encoded into messagesdepending upon message encoding scheme including, but not limited to,MIME extension for e-mail or XML tag.

To determine which location formats are accepted by message server 100,limits of location values, and defined zones, a message may be sent tomessage server 100 requesting the information. The information may besupplied inXML encoded format, for example.

A message address may be deleted be either the mobile user or themessage service provider. Also, it is desirable to eliminate unusedmobile IDs. A customer, for example, may have the option to specify howlong the address is valid.

The messaging service provider (e.g., mall management) may alsoexplicitly or implicitly limit the validity of the mobile addresses.Options may include, but are not limited to, adding temporary addressesdeleted at regular times, such as when the mall closes. Having mobileIDs deleted after a period of non-use, for example, one day with nomessages, or two days with stored messages. Also, mobile IDs may bedeleted at a user specified time. Further, a mobile ID may be deletedwhen the customer leaves the mall. In an exemplary embodiment, leavingthe mall may be differentiated from turning the device off.

Messages or mobile IDs may also be deleted if the number of messagesbeing stored or delivered becomes excessive (e.g., in the case of SPAMor mail bomb reaction).

EXAMPLE 1

Consider a retail shopping mall. Customers may use mobile devices (suchas PDAs) with wireless connections for various location based services.A customer requests a service (such as 1 hour photo service) in a storewithin the mall. The service will be complete at some time in the futureand the customer wishes to be notified when the service (photodeveloping) is complete.

The customer can communicate through a wireless technology (such as802.11 or Bluetooth) to a mall network support services for mobiledevices. The customer can request a mobile ID from the network. This IDis then passed to the photo store as the address to use for sendingnotices. When the customer' film is developed, the store can send amessage to him using his mobile ID.

The store may also choose to send a location specific message. If thecustomer is detected outside of the mall, they may send him anothermessage reminding him of the developed film.

Once the film is collected, location based messages should be cancelled(you don't want to bother the customer).

EXAMPLE 2

The same customer (as in example 1) is hungry, and wants to eat. Heselects a restaurant in the mall he wants to eat at, but it has awaiting list. Through his mobile device he requests a reservation (or tobe put on waiting list). He gives his mobile ID (same as example 1) tothe restaurant and asks to be notified when his table is ready.

When the customer's name is getting near the top of the list, therestaurant wants to warn the customer that his table will be ready soon.The restaurant sends the following messages:

-   -   When the customer is fifth on the list, send message to the far        locations of the mall.    -   When the customer is third on the list, they send message to the        medium distances away part of the mail and the previous message        is cancelled.    -   When the customer is first on the list, they send message to all        locations in mall and the previous message is cancelled.        When the customer receives the message, he can reply to        acknowledge he still wants the table.

EXAMPLE 3

The same customer goes into a store and asks a clerk for help in findingan item. The clerk says she will need to go and check the backroom. Shewill message him when she knows if the item is available.

The customer requests a new mobile ID, and gives it to the clerk. Afterlooking around the store, he decides he is not interested in the item,and cancels the mobile ID. There is no reason for the store to botherthe customer. He can still receive other messages (examples 1 and 2).The clerk may be notified of the cancelled ID, if she requestednotification in advance.

EXAMPLE 4

A husband and wife are shopping separately in the mall. If they are neareach other they would like to be informed. Both husband and wife sendeach other a message with a separation condition of 100 meters. Whenthey are within 100 meters, their messages are delivered. They may thencommunicate to see where the other is.

EXAMPLE 5

A meeting is schedule for 5:00 p.m. in conference room A. When themeeting is scheduled, a message is sent to everyone in the meeting withthe following conditions

-   -   Time 5:00 p.m.    -   Location (conference room A).        A reminder message is sent. If the meeting is altered, the        messages may be cancelled.

EXAMPLE 6

A mobile user enters a mall. He registers himself as a mobile user. Heregisters his handheld computer and pager. He queries the message serverand determines the server can support message redirection. He sends aconfiguration message to the message server stating than any messagesdestined for his handheld computer should be redirected to his pager.Whenever a message is sent to his handheld computer, the message serverredirects it to his pager. When he leaves the mall, he unregistershismobile_user, and all addresses are deleted.

While the detailed drawings, specific examples and particularformulations given describe preferred and exemplary embodiments, theyserve the purpose of illustration only. The inventions disclosed are notlimited to the specific forms shown. For example, the methods may beperformed in any of a variety of sequence of steps. The hardware andsoftware configurations shown and described may differ depending on thechosen performance characteristics and physical characteristics of thecomputing devices. For example, the type of computing device,communications bus, or processor used may differ. The systems andmethods depicted and described are not limited to the precise detailsand conditions disclosed. Furthermore, other substitutions,modifications, changes, and omissions may be made in the design,operating conditions, and arrangement of the exemplary embodimentswithout departing from the scope of the invention as expressed in theappended claims.

1. A messaging system comprising: a communications network including awireless access point; a messaging server coupled to the communicationsnetwork; a mobile device in communication with the communicationsnetwork via an access point, the mobile device having a mobile IDassociated with the device; a program running on the mobile deviceconfigured to enable a user to initiate creation of and dynamicallycreate, from the mobile device, a temporary address corresponding to themobile ID, the temporary address being useable for messaging over thecommunications network, the temporary address being registered with themessaging server and further being dynamically revocable upon userselection; an address translator of the messaging server, the translatortranslating an address of an incoming message to a correspondingtemporary address; and a mobile device state information unit, the unitkeeping track of the state of the mobile device, including location ofthe mobile device.
 2. The system of claim 1, wherein the program enablesthe deletion of a temporary address that is corresponding to the mobileID.
 3. The system of claim 1, wherein the program enables communicationof the temporary address to the messaging server.
 4. The system of claim1, wherein the program enables the forwarding of incoming messages viathe temporary address to alternative communications devices.
 5. Thesystem of claim 1, wherein the server is associated with a shopping mallenvironment.
 6. The system of claim 1, wherein the server is associatedwith a campus environment.
 7. The system of claim 1, wherein the mobiledevice is a handheld computer.
 8. The system of claim 1, wherein thecommunications network is a local area network (LAN).
 9. A method ofproviding messaging services to a user of a mobile communicationsdevice, comprising: providing a mobile device having a mobile IDassociated therewith; running a messaging program on the device;dynamically creating, via the program, a temporary messaging addressassociated with the mobile ID of the mobile device, wherein thetemporary messaging address is dynamically revocable upon userselection; communicating the temporary messaging address to a messagingserver; sending a message via the messaging server using the temporarymessaging address; translating a destination address to a correspondingtemporary messaging address; checking a mobile device state informationunit to determine whether the mobile device is in a state to receive themessage; and receiving by the messaging server an incoming messagehaving a destination address.
 10. The method of claim 9, furthercomprising: receiving, by the mobile communications device via themessaging server, a message addressed to the temporary messagingaddress.
 11. The method of claim 9, further comprising: creatingmultiple temporary messaging addresses associated with the mobile ID.12. The method of claim 11, further comprising: deleting multipletemporary messaging addresses associated with the mobile ID.
 13. Themethod of claim 9, further comprising: deleting a temporary messagingaddress associated with the mobile ID.
 14. The method of claim 9,further comprising: associating the temporary messaging address withmultiple mobile communication devices each mobile communication devicehaving a unique mobile ID.